Apparatus, system, and method for modifying an integration software template

ABSTRACT

An apparatus, system, and method are disclosed for modifying an integration software template. In one embodiment, a developer selects a template that employs a first code set from a library. A development module creates a project from a template using a developer input. A template modification module modifies the template in response to the project. A code generation module generates a second code set from the project. In one embodiment, an export module exports the second code set to the library.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to modifying tools and more particularly relatesto modifying an interface software template.

2. Description of the Related Art

A hub server is often used to provide computing resources to a pluralityof enterprise applications including web-based applications. Forexample, a hub server may be employed to host a web-based ordermanagement application, a data base application, and the like. Thecomputing resources may include database resources, data storageresources, processing resources, and the like.

The hub server may integrate one or more applications on a commonplatform or across disparate platforms. The integration of theapplications may allow the applications to share data, enhancing theusefulness of all applications. In integrating the applications, the hubserver may provide the computing resources for applications that arewritten specifically to interface with the hub server. For example, atransaction processing application may be written specifically tointerface with a specified hub server. In addition, the hub server mayprovide can computing resources for applications that are not written tointerface with the hub server. For example, the hub server may providecomputing resources to an inventory management system that was writtenfor use with a stand-alone inventory database.

In one embodiment, the hub server organizes computing resources asobjects. The objects are referred to herein as business objects.Business objects are objects specifically designed to satisfy needs ofone or more business processes. Business objects may comprisetransactions or events including one or more functions and employingelements in a data structure, elements of a database schema, or thelike. For example, a business object may include business object mayinclude a function to search a database column for a specifiedidentifier, and a function to retrieve a data value from the row of theidentifier.

The business objects of the hub server may be named and organizeddifferently from analogous objects of the applications interfacing withthe hub server. In addition, business objects may be generic and used tointerface with a plurality of applications. For example, a transactionprocessing application, a financial application, and an inventorymanagement application may each use a generic finished goods inventorybusiness object. The generic finished goods inventory object may includefunctions that sum data values in a database column.

The hub server may employ an adapter agent to interface with anapplication. Adapter agents provide prepackaged connectivity thatintegrates disparate industry-specific and cross-industry computingsystems by pulling and uniting information from packaged and customapplications; mainframe systems; technology protocols; databases; andtrading partners. The adapter agent may convert generic hub serverbusiness objects into objects employed by an application, referred toherein as application objects. Similarly, the adapter agent may convertan application object into a generic business object for use by the hubserver. For example, the adapter agent may convert an object thatretrieves a finished goods inventory sum value into the generic finishedgoods business object described above.

The hub server may employ an object discover agent (“ODA”) to discoverthe application objects associated with an application. In addition, theODA may generate a generic business object that is compatible with adiscovered application data object. For example, the ODA may communicatewith an application to discover the application objects employed by theapplication. The ODA may further generate equivalent generic businessobjects, mapping hub server functions and data to the application objectfunctions and data. Thus the ODA may create the businessobject/application object relationships that allow the adapter agent tointerface between the hub server and the application.

Tools have been developed to automate the creation of an ODA and/or anadapter adapter agent. For example, a user may employ an adaptertemplate to create an adapter agent that interfaces a hub server and anapplication. Tools reduce the time and cost of creating an ODA and/oradapter agent.

Unfortunately, the user may repeatedly make one or more similarcustomizing entries while using the tools to create a succession of ODAsand/or adapter agents for a particular hub server. For example, the usermay repeatedly enter a plurality of customizing entries specific to anapplication based on software produced by SAP AG of Walldorf, Germany.Although the tools may allow the user to create the ODAs and/or adapteragents more rapidly with fewer coding errors, the tools still do notautomate many of the important customizing functions.

From the foregoing discussion, it should be apparent that a need existsfor an apparatus, system, and method that modify an interface creationtool. Beneficially, such an apparatus, system, and method would reducethe time and cost of creating an ODA and adapter agent by incorporatingcommon customizing entries into the tool.

SUMMARY OF THE INVENTION

The present invention has been developed in response to the presentstate of the art, and in particular, in response to the problems andneeds in the art that have not yet been fully solved by currentlyavailable integration software template modification methods.Accordingly, the present invention has been developed to provide anapparatus, system, and method for modifying an integration softwaretemplate that overcome many or all of the above-discussed shortcomingsin the art.

The apparatus to modify an integration software template is providedwith a plurality of modules configured to functionally execute the stepsof creating a project, modifying a template comprising a first code set,and generating a second code set. These modules in the describedembodiments include a library, development module, a templatemodification module, and a code generation module.

The library includes a first code set. In one embodiment, the first codeset is an extensible markup language (“XML”) code set. The library alsoincludes an integration software template. As used herein, theintegration software template may be referred to as a template. Thetemplate may be an XML form. In a certain embodiment, the first XML codeset generates the XML form template. The library may include a pluralityof code sets and templates.

The development module creates a project from the template and adeveloper input. In one embodiment, the template is an adapter templatefor generating an adapter agent for interfacing between a hub server andan application. In an alternate embodiment, the template is an ODAtemplate for generating an ODA that specifies a business object frominteractions with the application.

The template modification module modifies the template in response tothe project. In one embodiment, the template modification modulemodifies the template by incorporating the developer input into thetemplate. In an alternate embodiment, the template modification modulemodifies the template by making the developer input available as aselectable template option.

The code generation module generates a second code set from the modifiedtemplate. In one embodiment, the second code set is an XML code set. Thesecond code set may be employed by the template to receive developerinputs. Alternatively, the second code set may generate a modifiedtemplate. The apparatus modifies the template by generating andemploying the second code set, allowing a developer to retain and reusemodifications.

A system of the present invention is also presented to modify anintegration software template. The system may be embodied in anintegration software system. In particular, the system, in oneembodiment, includes a library and a development suite. The developmentsuite includes a development module, a template modification module, acode generation module, and an export module.

The library includes a plurality of XML code sets and one or moretemplates that employ the code sets. The templates may be generated fromthe XML code sets. The development module creates a project from a firsttemplate employing a first XML code set using a developer input. Thetemplate modification module modifies the first template in response tothe project. The code generation module generates a second XML code setfrom the project. The export module may export the second XML code setto the library. The second XML code set in the library is employable bya second template.

In one embodiment, generating the second XML code set comprisesreplacing an input prompt of the first XML code set with a specifiedparameter. The first template may be an ODA template for an ODA thatspecifies a business object from interactions with an application.Alternatively, the first template may be an adapter template thatspecifies an adapter agent for interfacing between a hub server and anapplication. The system modifies the first template, generating thesecond XML code set that is reused to develop integration software viathe second template.

A method of the present invention is also presented for modifying anintegration integration software template. The method in the disclosedembodiments substantially includes the steps to carry out the functionspresented above with respect to the operation of the described apparatusand system. In one embodiment, the method includes creating a project,modifying a template comprising a first code set, and generating asecond code set.

In one embodiment, a developer selects a template that employs a firstcode set from a library. A development module creates a project from atemplate using a developer input. A template modification modulemodifies the template in response to the project. A code generationmodule generates a second code set from the project. In one embodiment,an export module exports the second code set to the library. The methodmodifies the template to preserve the developer input for futureprojects.

Reference throughout this specification to features, advantages, orsimilar language does not imply that all of the features and advantagesthat may be realized with the present invention should be or are in anysingle embodiment of the invention. Rather, language referring to thefeatures and advantages is understood to mean that a specific feature,advantage, or characteristic described in connection with an embodimentis included in at least one embodiment of the present invention. Thus,discussion of the features and advantages, and similar language,throughout this specification may, but do not necessarily, refer to thesame embodiment.

Furthermore, the described features, advantages, and characteristics ofthe invention may be combined in any suitable manner in one or moreembodiments. One skilled in the relevant art will recognize that theinvention may be practiced without one or more of the specific featuresor advantages of a particular embodiment. In other instances, additionalfeatures and advantages may be recognized in certain embodiments thatmay not be present in all embodiments of the invention.

The embodiment of the present invention modifies an integration softwaretemplate. In addition, the embodiment of the present invention mayexport a second code set that includes the template modifications to alibrary to allow subsequent reuse of the modifications. modifications.These features and advantages of the present invention will become morefully apparent from the following description and appended claims, ormay be learned by the practice of the invention as set forthhereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the advantages of the invention will be readilyunderstood, a more particular description of the invention brieflydescribed above will be rendered by reference to specific embodimentsthat are illustrated in the appended drawings. Understanding that thesedrawings depict only typical embodiments of the invention and are nottherefore to be considered to be limiting of its scope, the inventionwill be described and explained with additional specificity and detailthrough the use of the accompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of adata processing system in accordance with the present invention;

FIG. 2 is a schematic block diagram illustrating one embodiment of a hubserver/application system of the present invention;

FIG. 3 is a schematic block diagram illustrating one embodiment of anODA system of the present invention;

FIG. 4 is a schematic block diagram illustrating one embodiment of anintegration software template modification apparatus of the presentinvention;

FIG. 5 is a schematic block diagram illustrating one embodiment of acomputer in accordance with the present invention;

FIG. 6 is a schematic flow chart diagram illustrating one embodiment ofan integration software template modification method of the presentinvention;

FIG. 7 is a schematic flow chart diagram illustrating one embodiment ofa template modification process of the present invention;

FIG. 8 is a text diagram illustrating one embodiment of a code set ofthe present invention;

FIG. 9A is a drawing illustrating one embodiment of a template of thepresent invention;

FIG. 9B is a drawing illustrating one embodiment of a template withdeveloper input of the present invention;

FIG. 10 is a text diagram illustrating one embodiment of a modified codeset of the present invention; and

FIG. 11 is a drawing illustrating one embodiment of an updated templateof the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Many of the functional units described in this specification have beenlabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom VLSI circuits or gate arrays,off-the-shelf semiconductors such as logic chips, transistors, or otherdiscrete components. A module may also be implemented in programmablehardware devices such as field programmable gate arrays, programmablearray logic, programmable logic devices or the like.

Modules may also be implemented in software for execution by varioustypes of processors. An identified module of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object,procedure, or function. Nevertheless, the executables of an identifiedmodule need not be physically located together, but may comprisedisparate instructions stored in different locations which, when joinedlogically together, comprise the module and achieve the stated purposefor the module.

Indeed, a module of executable code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different storage devices, and may exist, atleast partially, merely as electronic signals on a system or network.

Reference throughout this specification to “one embodiment,” “anembodiment,”or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment of the present invention. Thus,appearances of the phrases “in one embodiment,” “in an embodiment,” andsimilar embodiment,” and similar language throughout this specificationmay, but do not necessarily, all refer to the same embodiment.

Furthermore, the described features, structures, or characteristics ofthe invention may be combined in any suitable manner in one or moreembodiments. In the following description, numerous specific details areprovided, such as examples of programming, software modules, userselections, network transactions, database queries, database structures,hardware modules, hardware circuits, hardware chips, etc., to provide athorough understanding of embodiments of the invention. One skilled inthe relevant art will recognize, however, that the invention may bepracticed without one or more of the specific details, or with othermethods, components, materials, and so forth. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring aspects of the invention.

FIG. 1 is a schematic block diagram illustrating one embodiment of adata processing system 100 in accordance with the present invention. Thesystem 100 includes one or more workstations 110, a network 115, abridge 120, a local area network (“LAN”) 125, one or more hub servers130, a storage network 150, and one or more storage systems 140. Inaddition, each storage system 140 may include one or more storagecontrollers 160 and one or more storage devices 170.

The workstations 110 may be computer workstations, terminals, laptopcomputers, personal digital assistants, communication devices, or thelike. The workstations 110 may communicate with the hub servers 130through the network 115, the bridge 120, and the LAN 125 as is wellknown to those skilled in the art. Each hub server 130 may provideservices for the workstations 110 and/or another hub server 130. The hubservers 130 may access the storage systems 140 through the storagenetwork 150. In one embodiment, the storage network 150 and storagesystems 140 are configured as a storage area network.

For example, the hub servers 130 may maintain one or more databases onthe storage systems 140. The data of the databases may be stored on thestorage devices 170 and be accessed using the storage controllers 160.In one embodiment, the hub servers 130 are WBI InterChange Serversproduced by IBM of Armonk, N.Y. In addition, the hub servers 130 mayexecute the WBI Framework produced by IBM.

In a prophetic example, a first hub server 130 a may maintain aninventory database on a first storage system 140. An accountingapplication may access the inventory database to, for example, determinea finished goods inventory. In one embodiment, the accountingapplication may execute on the first hub server 130 a. Alternatively,the accounting application may execute on a second hub server 130 b oron another connected server or computing system.

Continuing the prophetic example, the accounting application may beconfigured to interface directly with the first hub server 130 a.Alternatively, the accounting application may not be configured tointerface directly with the first hub server 130 a. As a result, aninterface is required to manage communications between the accountingapplication and the first hub server 130 a. The interface may be createdusing a template. The embodiment of the present invention supports andfacilitates modifying the template by incorporating customizing entriesto template in subsequent template instances as will be describedhereafter.

FIG. 2 is a schematic block diagram illustrating one embodiment of a hubserver/application system 200 of the present invention. The system 200includes a hub server 130 of FIG. 1 in communication with one or moreapplications 220. The description of the system 200 further refers toelements of FIG. 1, like numbers referring to like elements.

The hub server 130 is depicted executing an interchange module 210. Inone embodiment, the interchange module 210 is the WBI Framework producedby IBM of Armonk, N.Y. The interchange module 210 may provide anapplication 220 with access to one or more databases stored on one ormore storage systems 140. In addition, the interchange moduleinterchange module 210 may allow an application 220 to manipulate datain the databases.

Each application 220 communicates with the interchange module 210through an adapter agent 215. The application 220 includes one or moreapplication objects. Each application object comprises data and/orfunctions. The data may be data for a single record such as a databaserow, a plurality of records such as a data base column, or the like. Thefunctions may be a structured query language (“SQL”) function, anarithmetic function, a statistical function, or the like. In a propheticexample, the application object includes customer registration data anda function that creates a customer account for a customer from thecustomer registration data.

The adapter agent 215 may employ an application program interface(“API”) of the application 220 to communicate with the application 220.In a prophetic example, the application 220 may have a first API thatprovides an application object comprising an index value, index columnname, a data column name, and an SQL SELECT function. In addition, theapplication 220 may have a second API that receives a value thatcorresponds to the index value, index column name, and data column name.Thus in a prophetic example, the application 220 may provide through thefirst API the index value ‘245456,’ the column name ‘Customer_ID,’ thedata column name ‘Phone_num,’ and SELECT function, and may receive thevalue ‘(750) 123-4567’ through the second API in response to the firstAPI.

The interchange module 210 may include one or more business objects.Each business object may include one or more data attributes. In oneembodiment, the data attributes are referred to as attributes. A dataattribute may be a database schema column name, a column name and indexvalue, a view name, or the like. A business object may also include oneor more functions. In one embodiment, the functions are referred to asverbs. In a prophetic example, a business object function may determinethe mathematical mean of the values of a database schema column. In oneembodiment, the business object may be configured as a flat object, withconfigured as a flat object, with one array of data values.Alternatively, the business object may be hierarchical, wherein a parentarray of data values is linked to one or more child arrays of data.

The adapter agent 215 interfaces between the interchange module 210 andthe application 220 by converting an application object of theapplication 220 into a business object of the interchange module 210 andby converting the business object into an application object. In oneembodiment, an application API passes the application object to theadapter agent 215 and the adapter agent passes a business objectconverted from the application object to the interchange module 210.Similarly, the interchange module 210 may pass a business object to theadapter agent 215 and the adapter agent 215 may pass an applicationobject converted from the business object to an API of the application220.

FIG. 3 is a schematic block diagram illustrating one embodiment of anODA system 300 of the present invention. The system 300 includes an ODA305, an application 220, a database 310, and a file system 315. Inaddition, the description of the system 300 refers to elements of FIGS.1-2, like numbers referring to like elements.

The ODA 305 interacts with the application 220 and may interact with thedatabase 310, and/or the file system 315 to specify a business object.The ODA 305 may interface to the application 220 and retrieves a list ofdata names, function names, and the like that are supported by theapplication 220. The ODA 305 may employ a name of the application 220, auser identifier of an account with access to the application 220, apassword for the account, and the like to access the application 220. Inaddition, the ODA 305 may employ a table name, a schema name, a datavalue, or the like to retrieve the list of data names. Alternatively,the ODA 305 communicates with the application 200 using an API. In aprophetic example, the ODA 305 communicates the table name ‘Customers’to the application 220 to receive a list of all column names associatedwith the ‘Customers’ table of the application 220.

In addition, the ODA 305 may communicate with a database 310 and/or afile system 315 to retrieve lists of data names and/or functions. In aprophetic example, the database 310 may reside on a storage system 140of FIG. 1. The ODA 305 may communicate with the database 310 to receivea list of data names and/or functions of the database 310. In a certainembodiment, the ODA 305 communicates with the file system 315 to receivea list of files, data stores, data names, and the like.

In one embodiment, the ODA 305 specifies a business object by mappingone or more data names and functions of the application 220 with one ormore data names and functions of the database 310 and/or file system315. In a prophetic example, the ODA 305 may specify a business objectcomprising the application data name ‘Phone’ mapped to the database dataname ‘Phon_num’ along with an application retrieve function mapped to adatabase SQL SELECT function.

FIG. 4 is a schematic block diagram illustrating one embodiment of anintegration software template modification apparatus 400 of the presentinvention. The apparatus 400 includes a development module 405, templatemodification module 410, code generation module 415, export module 420,debug module 425, and library 430. In addition, the description of theapparatus 400 refers to elements of FIGS. 1-3, like numbers referring tolike elements.

The library 430 includes a first code set and a template. A developermay select the template from the library 430 for developing an adapteragent 215 and/or an ODA 305. In one embodiment, the first code set is anXML code set and the template is an XML form template. In a certainembodiment, the first XML code set generates the XML form template. Thelibrary 430 may include a plurality of code sets and templates. In oneembodiment, the library 430 incorporates a revision management function.

In one embodiment, the template is an adapter template for generating anadapter agent 215 for interfacing between the hub server 205 and theapplication 220. In an alternate embodiment, the template is an ODAtemplate for generating an ODA 305.

The development module 405 creates a project from the template and adeveloper input as will be described hereafter. The developer mayprovide the development module 405 with the developer input. Forexample, the developer input may be a selection and/or indication with acomputer pointing device such as a mouse, a text entry, or the like thatselects a configuration parameter.

The template modification module 410 modifies the template in responseto the project as will be described hereafter. In one embodiment, thedeveloper selects one or more developer inputs for use by the templatemodification module 410 in modifying the template. Alternatively, thetemplate modification module 410 may automatically modify the templateusing each developer input.

The code generation module 415 generates a second code set from themodified template. In one embodiment, the second code set is an XML codeset. The second code set may be employed by the template to receivedeveloper inputs. Alternatively, the second code set may generate anupdated template.

In one embodiment, the export module 420 exports the second code set tothe library 430 as will be described hereafter. In addition, the exportmodule 420 may build a run-time process such as an adapter agent 215and/or ODA 305 from the second code set.

In one embodiment, the debug module 425 debugs the run-time process. Ina prophetic example, the debug module 425 may record each operationperformed by the run-time process, along with the values of processorregisters, data values, and the like. The developer may display therecorded operations and values to find bugs that may be corrected usinga development tool such as the development module 405. The apparatus 400modifies the template by generating and employing the second code set,allowing a developer to retain and reuse configuration entries.

FIG. 5 is a schematic block diagram illustrating one embodiment of acomputer 500 in accordance with the present invention. The computer 500may be the workstation 110 and/or the hub server 130 of FIG. 1. Asdepicted, the computer 500 includes a processor includes a processormodule 505, a cache module 510, a memory module 515, a north bridgemodule 520, a south bridge module 525, a graphics module 530, a displaymodule 535, a basic input/output system (“BIOS”) module 540, a networkmodule 545, a universal serial bus (“USB”) module 550, an audio module555, a peripheral component interconnect (“PCI”) module 560, and astorage module 565. In addition, the description of the computer 500refers to elements of FIGS. 1-4, like numbers referring to likeelements.

The processor module 505, cache module 510, memory module 515, northbridge module 520, south bridge module 525, graphics module 530, displaymodule 535, BIOS module 540, network module 545, USB module 550, audiomodule 555, PCI module 560, and storage module 565, referred to hereinas components, may be fabricated of semiconductor gates on one or moresemiconductor substrates. Each semiconductor substrate may be packagedin one or more semiconductor devices mounted on circuit cards.Connections between the components may be through semiconductor metallayers, substrate-to-substrate wiring, circuit card traces, and/or wiresconnecting the semiconductor devices.

The memory module 515 stores software instructions and data. Theprocessor module 505 executes the software instructions and manipulatesthe data as is well know to those skilled in the art. In one embodimentthe processor module 505 executes and the memory module 515 stores oneor more software processes that embody the development module 405,template modification module 410, code generation module 415, exportmodule 420, debug module 425, and library 430.

In one embodiment, the library 430 may reside on a plurality of storagelocations in the memory module 515. The library 430 may organizetemplates and/or code sets as flat files, linked data arrays, or thelike. The developer may view the template through display module 535. Inaddition, the developer may provide the developer input through akeyboard and/or mouse in communication with USB module 550.

The schematic flow chart diagrams that follow are generally set forth aslogical flow chart diagrams. As such, the depicted order and labeledsteps are indicative of one embodiment of the presented method. Othersteps and methods may be conceived that are equivalent in function,logic, or effect to one or more steps, or portions thereof, of theillustrated method. Additionally, the format and symbols employed areprovided to explain the logical steps of the method and are understoodnot to limit the scope of the method. Although various arrow types andline types may be employed in the flow chart diagrams, they areunderstood not to limit the scope of the corresponding method. Indeed,some arrows or other connectors may be used to indicate only the logicalflow of the method. For instance, an arrow may indicate a waiting ormonitoring period of unspecified duration between enumerated steps ofthe depicted method. Additionally, the order in which a particularmethod occurs may or may not strictly adhere to the order of thecorresponding steps shown.

FIG. 6 is a schematic flow chart diagram illustrating one embodiment ofan integration software template modification method 600 of the presentinvention. The method 600 substantially includes the steps to carry outthe functions presented above with respect to the operation of thedescribed systems 100, 200, 300 and apparatus 400, 500 of FIGS. 1-5. Inaddition, the description of the method 600 refers to elements of FIGS.1-5, like numbers referring to like elements.

The method 600 begins, and in one embodiment, the developer selects 605a template that employs a first code set from the library 430. Thedeveloper may employ the computer 500 to select 605 the template, and toperform the steps described hereafter. In one embodiment, the developerrefers to a description to select the template. The description may beembedded in the template. Alternatively, the description may be recordedin a data store and indexed to the template.

The development module 405 creates 610 a project from a template using adeveloper input. The project may include one or more messages. Inaddition, the messages may be organized as a message file. The projectmay also include a process library. The process library may be anexternal process library such as a Java jar, a C++ library, or the like.The project may store one or more developer inputs with the selectedtemplate, message file, and process library.

The template modification module 410 modifies 615 the template inresponse to the project. In one embodiment, the template modificationmodule 410 modifies 615 the template by incorporating the developerinput into the template. In a prophetic example, the project includesthe template and a text entry developer input to the template. The textentry developer input may for example specify an application 220 byname. The template modification module 410 may modify 615 the templateby incorporating the text entry developer input within the template aswill be explained in relation to FIGS. 8-10.

In an alternate embodiment, the template modification module 410modifies 615 the template by making the developer input available as aselectable template option. Continuing the prophetic example, thetemplate modification module 410 may modify 615 the template by makingthe text entry developer input a selectable option on a drop-down menuof the template.

The code generation module 415 generates 620 a second code set from theproject. In one embodiment, the code generation module 415 generates 620the second code set from the modified template of the project. Inaddition, the code generation module 415 may employ elements of themessage file and/or process library. In a certain embodiment, the codegeneration module 415 incorporates the message file and the processlibrary with the second code set. In a prophetic example, the codegeneration module 415 may store the message file and a link to theprocess library with the second code set.

In one embodiment, the export module 420 builds 625 a run-time processfrom the second code set. The run-time process may be an adapter agent215. Alternatively, the run-time process may be an ODA 305. In oneembodiment, the export module 425 creates source code from the secondcode set. The source code may be Java code, C++ code, or the like. Theexport module 425 may further build 625 the run-time process from thesource code.

In one embodiment, the debug module 425 debugs 630 the run-time process.The debug module 425 may record the operations of the run-time processas the run-time process executes. The developer may configure the debugmodule 425 to trap on an operational event as is well known to thoseskilled in the art. In addition, the developer may view the operationsoccurring immediately before and after to operational event to find bugsin the project.

In one embodiment, the export module 420 exports 635 the second code setto the library 430. In a certain embodiment, the export module 420associates a description with second code set. The description may beappended to the second code set. Alternatively, the description may berecorded in a data store and indexed to the second code set. The method600 modifies 615 the template and preserves the developer inputmodifications for future projects.

FIG. 7 is a schematic flow chart diagram illustrating one embodiment ofa template modification process 700 of the present invention. Theprocess 700 shows the software elements that are employed and created bythe development module 405, template modification module 410, codegeneration module 415, export module 420, debug module 425, and library430 using the steps of the integration software template modificationmethod 600 of FIG. 6. The description of the process 700 refers toelements of FIGS. 1-6, like numbers referring to like elements.

The development module 405 creates 610 a project 720 from a template 715that is selected 605 from the library 430 and from one or more developerinputs 710. In one embodiment, the template 715 is an XML form. The XMLform template 715 may be generated from a first XML code set as is wellknown to those skilled in the art.

The developer may enter the developer inputs in the template 715. In aprophetic example, the developer may enter the name of an application220. In an alternate prophetic example, the developer may select a datacolumn name as the developer input. Those skilled in the art recognize avariety of possible developer inputs.

The template modification module 410 modifies 615 the template 715 inresponse to the project 720 to form a modified template 705. In aprophetic example that will be shown in more detail hereafter in FIGS.8-11, the template modification module 410 may modify 615 the template715 by incorporating the developer input into the template 715 to createthe modified template 705.

The code generation module 415 generates 620 a second code set 725 fromthe modified template 705. In one embodiment, the second code set 725 isan XML code set. Alternatively, the second code set 725 may be a Javacode set, metadata, or the like. In a certain embodiment, codegeneration module 415 redacts the second code set 725 from theunderlying XML code of the modified template 705.

In one embodiment, the export module 420 builds 625 a run-time process730 from the second code set 725. The export module 420 may translateXML code of the second code set 725 into source code such as Java, C++,or the like. The export module 420 may further encapsulate the Javasource code as a Java run-time process 730. Alternatively, the exportmodule 420 may compile the C++ source code as a run-time executableprocess 730.

In one embodiment, the debug module 425 debugs 630 the run-time process730. The developer may correct the project 720 with developer inputs tocorrect bugs found in the second code set 725. The hub server 205 mayexecute the run-time process 730 when the run-time process 730 isdebugged.

In one embodiment, the export module 420 exports 635 the second code set725 725 as a library code set 735 to the library 430. The export module420 may format the library code set 735 for use by one or more templates715. In a prophetic example, the template 715 may incorporate one ormore XML code sets. The export module 420 may format the library codeset 735 for incorporation with the template 715 as an XML code set byadding coded identifiers, commands, and the like to the second code set735.

The library 430 may store the library code set 735 created from thesecond code set 725 in a hierarchical structure wherein the library codeset 735 is indexed to the first code set. Alternatively, the library 430may index and store the library code set 735 using a description createdfor the second code set 725. The developer may employ the library codeset 735 to create another project 720 that includes and preserves themodifications that the developer made to the original project 720.

FIG. 8 is a text diagram illustrating one embodiment of a code set 800of the present invention. The code set 800 may be a first code set asdescribed previously. The description of the code set 800 refers toelements of FIGS. 1-7, like numbers referring to like elements. FIGS.8-11 comprise a prophetic example of the template modification process700 of FIG. 7.

The code set 800 is depicted as an XML code set. The code set 800includes a plurality of XML statements 805. The statements 805 maycomprise an XML form template 715. Included in the XML statements aretwo input statements 810 that receive data through input boxes on thetemplate 715 as will be illustrated in FIG. 9A. In addition, the XMLstatements 805 include two parameter statements 815 that define data.

FIG. 9A is a drawing illustrating one embodiment of a template 715 ofthe present invention. The template 715 is the template 715 of FIG. 7.The description of the template 715 refers to elements of FIGS. 1-8,like numbers referring to like elements.

The template 715 is depicted as generated from the code set 800 of FIG.8. The template 715 is shown as the template 715 may be displayed forthe developer on the display module 535 of FIG. 5. As depicted, thetemplate 715 includes one or more input labels 905 labels 905 and one ormore input boxes 910. A first input label 905 a is created from a firstinput statement 805 a. A second input label 905 b is also created from asecond input statement 805 b. The template 715 includes a first inputbox 910 a that is defined by the first input statement 805 a and isconfigured to receive a first data value as defined by a first parameterstatement 815 a. In the prophetic example, the first data value is apackage name. A second input box 910 b is defined by the second inputstatement 805 b and is configured to receive a second data value asdefined by a second parameter statement 815 b. In the prophetic example,the second data value is a target name.

FIG. 9B is a drawing illustrating one embodiment of a template 715 withdeveloper input 710 of the present invention. The template 715 of FIG.9A is depicted with a data value entered in the second input box 910 b.In one embodiment, the template 715 is the modified template 705 of FIG.7.

The developer may enter the data value as a configuration entry for theproject 720. While the data value may be used to build 625 a run-timeprocess 730, the embodiment of the present invention may also retain thedata value as part of the template 715 of a subsequent project 720.

The template modification module 405 may modify 615 the template 715with the developer input 710 to form a modified template 705. Themodified template 705 may incorporate the developer input 710 in thesecond input box 910 b.

FIG. 10 is a text diagram illustrating one embodiment of a modified codeset 1000 of the present invention. The modified code set 1000 depicts aprophetic example of the code set 800 of FIG. 8 as generated 620 by thecode generation module 415 from the template 715 of FIG. 9B. Thedescription of the modified code 1000 also refers to elements of FIGS.1-9B, like numbers referring to like elements. The modified code set1000 may be the second code set 725 and/or library code 735 of FIG. 7.

The modified code set 1000 is depicted as an XML code set. The modifiedcode set 1000 includes a plurality of XML statements 1005. The secondinput statement 810 b of FIG. 8 is modified to a statement 1010 thatspecifies the data value as “SAP.” Thus the developer need not specifythe target name as the second data value for the target name isincorporated in the modified code set 1000.

FIG. 11 is a drawing illustrating one embodiment of an updated template1100 of the present invention. The updated template 1100 is a propheticexample of the template 715 employing the modified code set 1000 of FIG.10. The description of the updated template 1100 refers to elements ofFIGS. 1-10, like numbers referring to like elements.

The updated template 1100 is depicted as generated from the modifiedcode set 1000 of FIG. 10. The first input statement 810 a creates thefirst input box 910 a as with the template 715 of FIG. 9A. However, thesecond input box 910 a of the template 715 of FIG. 9A is replaced with adisplayed data value 1105 specifying that the target name is “SAP.” Thusthe developer may preserve configuration entries to a template 715 inthe updated template 1100 for use with subsequent projects 720.

The embodiment of the present invention modifies a template 715. Inaddition, the embodiment of the present invention may export a secondcode set 725 that includes the template modifications to a library 430to allow subsequent reuse of the modifications.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. An apparatus to modify an integration software template, theapparatus comprising: a library comprising a first code set and atemplate that employs the first code set; a development moduleconfigured to create a project using the template and a developer input;a template modification module configured to modify the template inresponse to the project; and a code generation module configured togenerate a second code set from the modified template.
 2. The apparatusof claim 1, wherein generating the second code set comprises replacingan input prompt of the first code set with a specified parameter.
 3. Theapparatus of claim 1, wherein generating the second code set comprisesreplacing a first parameter of the first code set with a secondparameter.
 4. The apparatus of claim 1, wherein the first and secondcode sets are configured as extensible markup language (“XML”) code setsand the template is configured as an XML form.
 5. The apparatus of claim1, further comprising an export module configured to export the secondcode set to the library wherein the second code set is employable by thetemplate.
 6. The apparatus of claim 5, wherein the template isconfigured as an adapter template that specifies an adapter agent forinterfacing between a hub server and an application.
 7. The apparatus ofclaim 6, wherein the hub server is configured as an InternationalBusiness Machines Corporation (“IBM”) Websphere Business Integration(“WBI”) InterChange Server.
 8. The apparatus of claim 6, the exportmodule is further configured to build the second code set as an adapteragent.
 9. The apparatus of claim 1, wherein the first and second codesets are configured as Java-based code sets.
 10. The apparatus of claim1, wherein the first and second code sets are configured as C++-basedcode sets.
 11. The apparatus of claim 1, wherein the template isconfigured as an object discovery agent (“ODA”) template for an ODA thatspecifies a business object from interactions with an application.
 12. Acomputer program product comprising a computer readable medium havingcomputer readable program code programmed to modify an integrationsoftware template, the operations of the computer program productcomprising: creating a project using a template that employs a firstcode set and a developer input; modifying the template in response tothe project; and generating a second code set from the project.
 13. Thecomputer program product of claim 12, the operations further comprisingexporting the second code set to the library wherein the second code setis employable by the template.
 14. The computer program product of claim12, wherein generating the second code set comprises replacing an inputprompt with a specified parameter.
 15. The computer program product ofclaim 12, wherein generating the second code set comprises adding afirst parameter to a list of a parameters.
 16. The computer programproduct of claim 12, wherein the first and second code sets areconfigured as XML code sets and the template is configured as an XMLform.
 17. The computer program product of claim 12, the operationsfurther comprising selecting the template and first code set from thelibrary.
 18. The computer program product of claim 12, wherein thetemplate is configured as an adapter template that specifies an adapteragent for interfacing between a hub server and an application.
 19. Thecomputer program product of claim 18, the operations further comprisingbuilding the second code set as an adapter agent.
 20. The computerprogram product of claim 19, wherein the hub server is configured as anIBM WBI InterChange Server.
 21. The computer program product of claim19, the operations further comprising debugging the adapter agent. 22.The computer program product of claim 21, wherein debugging the adapteragent comprises recording information from the adapter agent as theadapter agent executes on the hub server.
 23. The computer programproduct of claim 12, wherein the template is configured as an ODAtemplate for an ODA that specifies a business object from interactionswith an application.
 24. The computer program product of claim 23, theoperations further comprising building the second code set as an ODA.25. The computer program product of claim 12, wherein the first andsecond code sets are configured as Java-based code sets.
 26. Thecomputer program product of claim 12, wherein the first and second codesets are configured as C++-based code sets.
 27. A system to modify anintegration software template, the system comprising: a librarycomprising a first XML code set and a first template employing the firstXML code set; a development suite comprising a development moduleconfigured to create a project using the first template and a developerinput; a template modification module configured to modify the firsttemplate in response to the project; a code generation module configuredto generate a second XML code set from the project; and an export moduleconfigured to export the second XML code set to the library wherein thesecond XML code set is employable by a second template.
 28. The systemof claim 27, wherein generating the second XML code set comprisesreplacing an input prompt of the first XML code set with a specifiedparameter.
 29. The system of claim 27, wherein generating the second XMLcode set comprises replacing a first parameter of the first XML code setwith a second parameter.
 30. The system of claim 27, wherein the firstand second templates are XML forms.
 31. The system of claim 27, whereinthe template is configured as an adapter template that specifies anadapter agent for interfacing between a hub server and an application.32. The system of claim 27, wherein the template is configured as an ODAtemplate for an ODA that specifies a business object from interactionswith an application.
 33. A method for modifying an integration softwaretemplate, the method comprising: receiving an integration softwaretemplate modification input; providing the integration software templatemodification input to a development tool suite the development suitecomprising a library comprising a first XML code set and a templateemploying the first XML code set; a development module configured tocreate a project from the template and a developer input; a templatemodification module configured to modify the template in response to theproject and the integration software template modification input; a codegeneration module configured to generate a second XML code set from theproject; an export module configured to export the second XML code setto the library wherein the XML second code set is employable by thetemplate; and providing the second code set to a customer.
 34. Themethod of claim 33, wherein the template is configured as an adaptertemplate that specifies an adapter agent for interfacing between a hubserver and an application.
 35. An apparatus to modify an integrationsoftware template, the apparatus comprising: means for selecting atemplate that employs a first XML code set from a library; means forcreating a project using the template and a developer input; means formodifying the template in response to the project; means for generatinga second XML code set from the project; means for exporting the secondXML code set to the library wherein the second XML code set isemployable by the template; means for building the XML second code setas an adapter agent for interfacing a hub server and an application.